Medway Council

Tree preservation zone

There is a problem

• 1 row is missing a geometry

entity: 19128491

• reference: M1-1998
• geometry:

  geometry missing

  MULTIPOLYGON (((0.501016 51.388875,0.501026 51.388881,0.501024 51.388890,0.500995 51.388889,0.500999 51.388877,0.501016 51.388875)),((0.501111 51.388832,0.501122 51.388839,0.501118 51.388847,0.501093 51.388844,0.501096 51.388834,0.501111 51.388832)),((0.501082 51.388843,0.501094 51.388851,0.501090 51.388860,0.501062 51.388857,0.501065 51.388846,0.501082 51.388843)),((0.500979 51.388887,0.500990 51.388890,0.500990 51.388903,0.500962 51.388902,0.500965 51.388889,0.500979 51.388887)),((0.500951 51.388895,0.500957 51.388900,0.500952 51.388910,0.500938 51.388912,0.500927 51.388904,0.500937 51.388893,0.500951 51.388895)))
• point: POINT (0.50102 51.388876)
• entry-date: 2025-01-18
• start-date: 1998-05-12

How to fix this issue

Your dataset is missing the geometry column.

The Tree preservation zone guidance explains how to fix the issue:

geometry

The boundary for the tree preservation zone as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Medway Council’s data

1. Fix the errors indicated
2. Use the check service to make sure the data meets the standard
3. Publish the updated data on the endpoint URL